Internet Info 1997 December/Internet_Info_CD-ROM_Walnut_Creek_December_1997.iso/ietf/urn/urn-archives/urn-ietf.archive.9710/000012_owner-urn-ietf _Mon Oct 27 14:35:04 1997.msg

Internet Message Format | 1997-10-28 | 5KB

Received: (from daemon@localhost)
    by services.bunyip.com (8.8.5/8.8.5) id OAA25221
    for urn-ietf-out; Mon, 27 Oct 1997 14:35:04 -0500 (EST)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1])
    by services.bunyip.com (8.8.5/8.8.5) with ESMTP id OAA25205
    for <[e-mail]>; Mon, 27 Oct 1997 14:34:58 -0500 (EST)
Received: from beethoven.bunyip.com (beethoven.Bunyip.Com [192.197.208.5])
    by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id OAA04420;
    Mon, 27 Oct 1997 14:33:31 -0500 (EST)
Received: from localhost (leslie@localhost) by beethoven.bunyip.com (8.6.9/8.6.10) with SMTP id OAA05768; Mon, 27 Oct 1997 14:33:40 -0500
X-Authentication-Warning: beethoven.bunyip.com: leslie owned process doing -bs
Date: Mon, 27 Oct 1997 14:33:39 -0500 (EST)
From: Leslie Daigle <[e-mail]>
To: Dan Connolly <[e-mail]>
cc: [e-mail], [e-mail], [e-mail],
        [e-mail], [e-mail],
        [e-mail], [e-mail], [e-mail], [e-mail],
        [e-mail], [e-mail], [e-mail], [e-mail],
        [e-mail], [e-mail]
Subject: [URN] Re: The UR* scheme registry, Citing URL/URI specs
In-Reply-To: <[e-mail]>
Message-ID: <[e-mail]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: [e-mail]
Precedence: bulk
Reply-To: Leslie Daigle <[e-mail]>
Errors-To: [e-mail]

[At this point, many other people have replied to several points in this
message, so rather than just adding "me too" to what has been said adequately,
I'll only address points that still seem to be outstanding.  Dan, if
you still want more detail on things I leave out, please let me know. -- LLD]

On Fri, 24 Oct 1997, Dan Connolly wrote:
> Short version:
>
> Leslie Daigle wrote:
> > >      Syntax draft says "URIs are covered by other specs".
> > >      What other specs?
> >
> > RFC2141
>
> Hmmm.... checking...
> The term URI does not occur in RFC2141.
> So that's no help.

Well, I responded to the larger excerpt from the "syntax" draft (which
I assume is draft-fielding-url-syntax-09.txt) which says:

   "The syntax and semantics of other
    URIs are defined by a separate set of specifications, although
    it is expected that any URI notation would have a compatible syntax."

RFC2141 is an appropriate reply to _this_ quote, as it says that _other_
URI specs are defined elsewhere.  I had misunderstood that you had
read it to mean that _URI_ syntax was covered elsewhere.

By the way -- note that this is the

    "Uniform Resource Locators (URL): Generic Syntax and Semantics"

draft, and it's the "and semantics" parts that concerns me particularly
when talking about sweeping URN syntax into this and calling it the URI
syntax document.

> > > don't reflect that. The IANA registry[1] claims to be
> > > a URL scheme registry, rather than a URI scheme
> > > registry. So I wonder... is it expected that urn: will
> > > appear in that registry?
> >
> > Not necessarily.
>
> Can I please have a clear "yes" or "no" from your
> own personal perspective? Do you expect it to
> go in that list or not?

Well, there are 2 separate questions on the table:

    1.  Does "URN:" appear in this registry as one UR{I|L} scheme?

    2.  Do URN namespaces (i.e., that part that appears after the URN:
        e.g., urn:ietf:<blah>) get registered in that registry.  You
        suggest not; Larry later suggested he thought they ought.

If the IANA registry is truly to be the URI registry, and an informed
discussion (i.e., by people who know about that registry AND the current
state of URNs) shows this will not restrict the usage of URNs, then sure,
the answer to #1 is yes, urn: can/should appear there (and a ghost of myself
from a couple of years ago just passed out in shock that I said that ;-)

#2 is a definite "no"; URN namespaces are _not_ just like URL schemes.  THey
have implications of ownership, maintaingin registries and validation
services, and a whole set of requirements centred on uniqueness, etc.  I'm
sorry to be so vague here -- this is exactly the part that the URN WG
is trying to nail down now (and if I could be less vague, I'd be halfway
to having the I-D written :-)

> But I haven't run into one that told me how they're
> currently using them (except for PURLs, which use the http:
> scheme,  [...]

They exist -- if you need specific pointers, I can send them to you
out-of-band.

Leslie.

----------------------------------------------------------------------------

  "_Be_                                           Leslie Daigle
             where  you
                          _are_."                 Bunyip Information Systems
                                                  [phone]
                      -- ThinkingCat              [e-mail]
----------------------------------------------------------------------------